feat: add web.useInternalFrontend option for Web UI#850
Closed
ivankovnatsky wants to merge 1 commit intotemporalio:mainfrom
Closed
feat: add web.useInternalFrontend option for Web UI#850ivankovnatsky wants to merge 1 commit intotemporalio:mainfrom
ivankovnatsky wants to merge 1 commit intotemporalio:mainfrom
Conversation
When server-side authorization is enabled, the Web UI cannot connect to the frontend service (port 7233) because it does not send authorization credentials. The internal-frontend service bypasses the authorizer and is already used by admintools and schema jobs in this scenario. This adds a `web.useInternalFrontend` option (default: false) that, when enabled alongside `server.internal-frontend.enabled`, points the Web UI at internal-frontend instead of frontend. This allows the Web UI to operate without server-side authorization. Users who want authenticated Web UI access (e.g., via SSO/OIDC) can leave this as false and configure TEMPORAL_AUTH_* environment variables. Note: TEMPORAL_ADDRESS cannot be overridden via web.additionalEnv because the template renders the hardcoded value first, and Kubernetes silently drops duplicate environment variable names (keeping the first occurrence).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was changed
Added a
web.useInternalFrontendoption (default:false) tovalues.yamland a conditional in
web-deployment.yamlthat points the Web UI atinternal-frontendinstead offrontendwhen enabled.Files changed:
charts/temporal/templates/web-deployment.yaml— conditionalTEMPORAL_ADDRESSbased onweb.useInternalFrontendandserver.internal-frontend.enabledcharts/temporal/values.yaml— newweb.useInternalFrontend: falsewith documentationWhy?
We would like to have an option to pass through auth as admintools and others
too. Only configuring auth for the api for now.
Checklist
Closes — N/A (no existing issue for this)
How was this tested:
Verified with
helm templatethat both cases render correctly:Also tested on a live staging deployment — Web UI successfully connects and
displays data when pointed at internal-frontend.
The
values.yamlcomment documents the option.The Web UI environment variables reference
on docs.temporal.io could mention this option, but it is not strictly required.